I'm getting the following error after attempting a three mailbox move from one Exchange 2010 SP2 database to another on the same server. All the similar errors I've seen while searching are between 2010 and 2003 or 2007. Warning: Failed to clean up the source mailbox after the move. Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634) The move shows "Completed with warnings" as status, and I don't know how to clean the failed cleanup up. I HAVE been able to move mailboxes from one mailbox database before on this server. The log of move move shows the following, notice at one point the log says the cleanup is done, but then throws a "failed" flag and attempts cleanup 5 more times. This server has NOT had RU 3 applied. 6/25/2012 4:58:01 PM [HUB_Server] Move has completed and final clean up has started. 6/25/2012 4:58:01 PM [HUB_Server] Source mailbox 'Primary (58a48cb1-ff66-4893-a352-436ecd328504)' was successfully cleaned up after the move. 6/25/2012 4:58:01 PM [HUB_Server] Relinquishing job. 6/25/2012 4:58:06 PM [HUB_Server] The Microsoft Exchange Mailbox Replication service 'GATE5.evergreen.edu' (14.2.297.0 caps:07) is examining the request. 6/25/2012 4:58:06 PM [HUB_Server] Connected to target mailbox 'Primary (58a48cb1-ff66-4893-a352-436ecd328504)', database 'NoQuotasDtoF', Mailbox server '<Mailbox_Server>' Version 14.2 (Build 247.0). 6/25/2012 4:58:06 PM [HUB_Server] Mailbox move is already finished. 6/25/2012 4:58:06 PM [HUB_Server] Move has completed and final clean up has started. 6/25/2012 4:58:06 PM [HUB_Server] Failed to clean up the source mailbox 'Primary (58a48cb1-ff66-4893-a352-436ecd328504)' after the move. Attempt 1/6. Error details: MapiExceptionUnexpectedMailboxState MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634) at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException) at Microsoft.Mapi.ExRpcAdmin.DeletePrivateMailbox(Guid guidMdb, Guid guidMailbox, Int32 flags) at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.DeleteMailboxInternal(Int32 flags) at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass2a.<Microsoft.Exchange.MailboxReplicationService.IMailbox.DeleteMailbox>b__29() at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation) at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.DeleteMailbox(Int32 flags) at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass6d.<PostMoveCleanupSourceMailbox>b__6b() at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate) 6/25/2012 4:58:06 PM [HUB_Server] Target mailbox 'Primary (58a48cb1-ff66-4893-a352-436ecd328504)' was successfully reset after the move. 6/25/2012 4:58:07 PM [HUB_Server] Post-move cleanup failed. The operation will try again in 30 seconds (1/6). 6/25/2012 4:58:37 PM [HUB_Server] Failed to clean up the source mailbox 'Primary (58a48cb1-ff66-4893-a352-436ecd328504)' after the move. Attempt 2/6.~bc

Hi Is the message "completing with warnings" for few users or all the users? Could these user access mailbox via OWA? What RU is your SP2? Did it upgrade to RU3? Also I Found a thread Failed to cleanup the source mailbox after the move http://social.technet.microsoft.com/Forums/en/exchange2010/thread/43c11f0e-450e-4ff1-9163-2cb801e2e1e0 And it mentioned that it is a known issue with Exchange 2003 and a hotfix KB940012 could help http://support.microsoft.com/kb/940012 Please have a try Cheers Zi Feng TechNet Community Support

Hi Is the message "completing with warnings" for few users or all the users? Could these user access mailbox via OWA? What RU is your SP2? Did it upgrade to RU3? Also I Found a thread Failed to cleanup the source mailbox after the move http://social.technet.microsoft.com/Forums/en/exchange2010/thread/43c11f0e-450e-4ff1-9163-2cb801e2e1e0 And it mentioned that it is a known issue with Exchange 2003 and a hotfix KB940012 could help http://support.microsoft.com/kb/940012 Please have a try Cheers Zi Feng TechNet Community Support

I am having this issue as well after installing Rollup 3 for Exchange 2010 SP2. We have never had Exchange 2003 in our environment so the older solutions do not apply. Warning: Failed to clean up the source mailbox after the move. Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634) 7/5/2012 1:17:35 PM [SERVER] Post-move cleanup failed. The operation will try again in 30 seconds (5/6). 7/5/2012 1:18:06 PM [SERVER] Failed to clean up the source mailbox 'Primary (35cbb3c7-afed-459f-9fb7-55edf7c4cdc2)' after the move. Attempt 6/6. Error details: MapiExceptionUnexpectedMailboxState MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634) at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException) at Microsoft.Mapi.ExRpcAdmin.DeletePrivateMailbox(Guid guidMdb, Guid guidMailbox, Int32 flags) at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.DeleteMailboxInternal(Int32 flags) at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass2a.<Microsoft.Exchange.MailboxReplicationService.IMailbox.DeleteMailbox>b__29() at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation) at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.DeleteMailbox(Int32 flags) at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass6d.<PostMoveCleanupSourceMailbox>b__6b() at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate) 7/5/2012 1:18:06 PM [SERVER] Request is complete.

This is for SP2 RU 3. The failure is for a few mailboxes, not all of them. Yes, the users can access their mailboxes, it is just I'm left with a "failure to cleanup" after moving. Again, this happens when moving mailboxes from one database to another ON THE SAME SERVER (Exchange 2003 is NOT involved).~bc

I have same problem as you, after installing RU3, in move request log: Post-move cleanup failed. The operation will try again in 30 seconds - it appears 3times or 4times. I must move 4500 mbxes, most of them with zero or small data, but "completing" status blocked processing of next local move requests for 2 or 3 minutes. Only one option for me was modification of MSExchangeMailboxReplication.exe.config see here: http://social.technet.microsoft.com/Forums/en-us/exchange2010/thread/027afd76-0be0-4ff7-aa09-64f17b872285 Move requests was between two Ex2010SP2 servers only. Hard to say how to repair :-( On Exchange 2010 SP2 without any RU it was fast and easy to move such huge amount of mailboxes without problem in few hours. I am not able to found how to change retry time 30 seconds for post-move clean-up.

We are running Exchange 2010 SP2 UR3 and also have the same issue. I'm moving about 125 mailboxes from DB1 to a new DB01 (DAG - but active copies are both on the same server). Error in Move Request Log: 7/11/2012 12:10:49 PM [CAVTMASE131] Post-move cleanup failed. The operation will try again in 30 seconds (1/6). 7/11/2012 12:11:19 PM [CAVTMASE131] Post-move cleanup failed. The operation will try again in 30 seconds (2/6). 7/11/2012 12:11:50 PM [CAVTMASE131] Post-move cleanup failed. The operation will try again in 30 seconds (3/6). 7/11/2012 12:12:21 PM [CAVTMASE131] Post-move cleanup failed. The operation will try again in 30 seconds (4/6). 7/11/2012 12:12:52 PM [CAVTMASE131] Post-move cleanup failed. The operation will try again in 30 seconds (5/6). 7/11/2012 12:13:23 PM [CAVTMASE131] Request is complete. Each outlook client disconnects for about 2 minutes when the move is at approximately 95%, but they are completing and functionality seems to be OK. DQ

Hi, Does anyone have a fix for this? I am currently moving from Exchange 2003 to 2010 and before I installed SP2 RU3 the mailboxes moved fine. I was hoping RU4 release yesterday would fix this issue but it didn't I would like to have a fix ASAP as I have 100+ mailboxes and at 6 extra minutes per mailbox that's around 10 extra hours just in waiting. Our setup is very simple with one Exchange 2003 standard SP2 machine moving to one Exchange 2010 box. Thanks, Ken

We are seeing the same issue in an Exchange 2010 SP2 RU3 environment with 15,000 mailboxes. We didn't see it before RU3 but we did RU3 and SP2 over the same weekend. The impact is that it breaks online mailbox moves for Ex2010 to Ex2010 moves.... We're seeing clients loss contact with the mailbox during the retries...

Hi All Has anyone managed to resolve this ? or find a fix We are experiancing the same issue with exchange 2010 SP2 RU2 It was working fine with SP1 LeeIT Team Leader Zycko LTD.

I haven't. I'm just deleting them as I go. I'd suggest you create a new post as I think this one is fairly dead.~bc

We are experiencing the same issue now, after installed SP2 & RU4, when moving mailboxes from one DB to another on the same Exchange 2010. So far no problems when moving mailboxes from Exchange 2007 into this new DB of E2010. And there were no problems a few months back (before SP2 RU4 installed) moving mailboxes on the same server between other two DBs. And the mailboxes which have "completed with warning" look like disconnected on the source DB side. Does anyone have a fix? Thanks, Eric

Same here... SP2 RU4 and had two out of 85 mailboxes finish with the same error... Anybody??? Bueller???

I don't think anyone but me is reading this tread. Your best bet is to start a new one.~bc

I think I found a workaround to the issue. It looks like this is a bug with sp2 ru4 To workaround the issue please follow the below: To Clean up a Soft Deleted Mailbox on a database: Get-MailboxStatistics -Database <MAILBOXDATABASE> | Where { $_.DisconnectReason -eq "SoftDeleted" } | Format-List LegacyDN, DisplayName, MailboxGUID, DisconnectReason Remove-StoreMailbox Database <MAILBOXDATABASE> Identity <MAILBOXGUID> MailboxState Softdeleted To Clean up all Soft Deleted Mailboxes on a database: Get-MailboxStatistics Database <MAILBOXDATABASE> | Where-Object {$_.DisconnectReason eq Softdeleted} | ForEach {Remove-StoreMailbox Database $_.database identity $_.mailboxguid MailboxState Softdeleted}IT Team Leader Zycko LTD.

I think I found a workaround to the issue. It looks like this is a bug with sp2 ru4 To workaround the issue please follow the below: To Clean up a Soft Deleted Mailbox on a database: Get-MailboxStatistics -Database <MAILBOXDATABASE> | Where { $_.DisconnectReason -eq "SoftDeleted" } | Format-List LegacyDN, DisplayName, MailboxGUID, DisconnectReason Remove-StoreMailbox Database <MAILBOXDATABASE> Identity <MAILBOXGUID> MailboxState Softdeleted To Clean up all Soft Deleted Mailboxes on a database: Get-MailboxStatistics Database <MAILBOXDATABASE> | Where-Object {$_.DisconnectReason eq Softdeleted} | ForEach {Remove-StoreMailbox Database $_.database identity $_.mailboxguid MailboxState Softdeleted}IT Team Leader Zycko LTD.

Hi. I also have this problem at a customer that is doing a migration from Exchange 2007 to Exchange 2010. All Exchange 2010 servers with SP2 and the last Rollup patch. When do you run this powershell commands? When the move-mailbox says "Completing"? Or after all the mailbox move says Completed? //Glenn

Just wanted to chime in and advise I am seeing the same problem. 2010 SP1 to 2010 SP2 RU4. Created a new DB and moving the mailboxes across does exactly the same thing - sits at 6 attempts to clean up the old database. Could this be a problem moving between databases created in Exchange PRE-SP2 and if I recreate all my mailbox databases in SP2 it will go away? I am in the process of doing this anyway (we need SP2 to fix a whitespace issue) so am moving all mailboxes to new databases. I will report back if moving between native SP2 databases gives the same error. Does anyone know what the mailbox cleanup post move actually does? Even mailboxes that show as "completed" and not "completed with warnings" still appear in the disconnected mailbox so it isn't removing soft deleted mailboxes if that is what it is meant to do?

Do you guys have the option "Don't permanently delete items until the database is backed up" selected on the source database settings by any chance? I have unticked this and don't seem to get the failure now. I still see " Post-move cleanup failed. The operation will try again in 30 seconds" but not the failure about deleting the source mailbox? EDIT: Scratch that - it still does it randomly so must have had a lucky streak!!

You run the command when the status of the Move Request status is "Completed with warning"

From Experts-Exchange: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27860728.html#a38404595 Excerpt: Soft-deleted mailboxes - When mailboxes are moved from a Microsoft Exchange Server 2010 database to any other database, Exchange doesn't fully delete the mailbox from the source database upon completion of the move. Instead, the mailbox in the source mailbox database is switched to a soft-deleted state. With soft-deleted mailboxes, you can use the MailboxRestoreRequest cmdlet set to access mailbox data during a mailbox restore operation. Soft-deleted mailboxes are retained in the source database until either the deleted mailbox retention period expires or until the Remove-StoreMailbox cmdlet is used to purge the mailbox The command seems to be doing the same as a good, old Exchange 2003 Purge command (remember when deleted mailboxes had a red X and you could right-click and purge them from the database before the retention time did it automatically for you?) :-)

Yeah but even mailboxes marked as "completed" and not with warnings still appear in disconnected mailboxes so aren't purged! I'm not too bothered about the old mailboxes that sit in a disconnected state on the old database as that is how it worked in SP1 and they will be cleaned up eventually automatically, the problem I have is the large number of mailboxes that need to be moved which will now take hours and hours longer than before (due to retrying every 30 seconds for 6 tries that is at least 3 minutes per mailbox even if they are empty which adds 300 minutes per 100 mailboxes or 5 hours!).